System and method for processing medical claims

ABSTRACT

A computer-implemented system for processing medical claims is disclosed. The system includes a medical device configured to be manipulated by a user while the user performs a treatment plan; a patient interface associated with the medical device, the patient interface comprising an output configured to present telemedicine information associated with a telemedicine session; and a processor. During the telemedicine session, the processor is configured to receive information from a medical device. Using the device-generated information, the processor is further configured to determine device-based medical coding information. The processor is further configured to transmit the device-based medical coding information to a claim adjudication server.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 17/021,895, filed Sep. 15, 2020, titled “Telemedicine forOrthopedic Treatment,” which claims priority to and the benefit of U.S.Provisional Patent Application Ser. No. 62/910,232, filed Oct. 3, 2019,titled “Telemedicine for Orthopedic Treatment,” the entire disclosuresof which are hereby incorporated by reference for all purposes. Thisapplication also claims priority to and the benefit of U.S. ProvisionalPatent Application Ser. No. 63/028,392, filed May 21, 2020, titled“System and Method for Processing Medical Claims,” the entire disclosureof which is hereby incorporated by reference for all purposes.

TECHNICAL FIELD

This disclosure relates generally to systems and methods foradjudication of medical device claims.

BACKGROUND

Electronic medical record (EMR) systems may be used to generate andmaintain an electronic record of health-related information relating toor about individuals within a health care organization. Thehealth-related information may be input by a variety of entities, e.g.,the individuals' health care providers, where such entries may be madeby any medically-related entity or its representatives, for example:administrators, nurses, doctors, or other authorized individuals;insurance companies; billing companies; hospitals; testing centers, suchas those related to radiologic services, blood and bodily fluid testingservices; and psychological service providers, such as psychologists,social workers, addiction and other counselors, and psychiatrists. Eachhealthcare service may have one or more medical billing codes, forexample Diagnosis-Related Group (DRG) and/or InternationalClassification of Diseases (ICD) codes, e.g., ICD-10, assigned forbilling purposes. Some of the individual's EMRs, including the one ormore medical billing codes, may be transferred to a third-party payor,such as an insurance company, for invoicing the individual's medicalclaims for the individual's healthcare services. A medical claim, or aclaim, is a medical bill, or bill, submitted to a health insurancecarrier, or other party responsible for payment, for services renderedand/or goods provided to patients by health care providers. After amedical claim is submitted to the insurance company, the insurancecompany determines its financial responsibility for the payment to thehealthcare provider (i.e., claim adjudication). The insurance companymay have procedures to ensure that no false medical claims are approvedfor payment, for example, by rejecting payment for medical billing codesinconsistent with the healthcare services provided. As a result of suchprocedures, the insurance company may decide to pay the medical claim infull, reduce the medical bill, deny the full medical claim, or revisethe nature of the claim such that it becomes eligible for full orpartial payment.

Medical billing may present difficulties in medical billing codeadjudication, often making it difficult for the healthcare provider tobe paid for its healthcare services. The data transfer from thehealthcare provider to the insurance company may not always be reliable,due in part to the volume of data, data security, and data consistencyissues (i.e., errors in the information). Further, human error ormalicious interlopers can reduce the reliability of such systems. Theuse of telemedicine may result in additional risks related to fraud,waste, and abuse, risks which bad actors can exploit. For example, if,at a location other than a healthcare facility, the medical device isbeing used, a healthcare provider may not oversee the use (e.g.,treatment, rehabilitation, or testing), and therefore, the healthcareprovider may not be able to easily confirm or validate the accuracy ofthe medical billing Further, mass transfer of this data as data packetsbetween various parts of the systems may increase network loads and slowprocessing time.

SUMMARY

In general, the present disclosure provides a system and methods forprocessing medical claims based on medical services. Such medicalservices may have been performed by an individual, by a medical device,or by combinations thereof, e.g., individuals using certain medicaldevices.

An aspect of the disclosed embodiments includes a computer-implementedsystem for processing medical claims. The computer-implemented systemincludes a medical device configured to be manipulated by a user whilethe user performs a treatment plan; a patient interface associated withthe medical device, the patient interface comprising an outputconfigured to present telemedicine information associated with atelemedicine session; and a processor. During the telemedicine session,the processor is configured to receive information from a medicaldevice. Using the device-generated information, the processor is furtherconfigured to determine device-based medical coding information. Theprocessor is further configured to transmit the device-based medicalcoding information to a claim adjudication server.

An aspect of the disclosed embodiments includes a system for processingmedical claims. The system includes a processor configured to receivedevice-generated information from a medical device. Using thedevice-generated information received, the processor is configured todetermine device-based medical coding information. The processor isfurther configured to transmit the device-based medical codinginformation to a claim adjudication server.

An aspect of the disclosed embodiments includes a method for a clinicserver to process medical claims. The method includes receivinginformation from a medical device. The method further includes, usingthe device-generated information, determining device-based medicalcoding information. The method further includes transmitting thedevice-based medical coding information to a claim adjudication server.

An aspect of the disclosed embodiments includes a tangible,non-transitory computer-readable medium. The tangible, non-transitorycomputer-readable medium stores instructions that, when executed, causea processor to receive device-generated information from a medicaldevice. Using the device-generated information received, the processordetermines device-based medical coding information. The processorfurther transmits the device-based medical coding information to a claimadjudication server.

In yet another aspect, a system for generating and processing medicalbilling codes is disclosed. The system includes a medical device and acomputing device. The computing device comprises a processor incommunication with the medical device. The processor is configured toreceive information from the medical device and transmit thedevice-generated information to a clinic server. Using thedevice-generated information received, the processor is configured todetermine device-based medical coding information. The processor isfurther configured to cause the clinic server to transmit thedevice-based medical coding information to a claim adjudication server.

An aspect of the disclosed embodiments includes a method for operating amedical device. The method includes receiving information from themedical device. The method further includes transmitting thedevice-generated information to the clinic server. Using thedevice-generated information received, the method further includescausing the clinic server to determine device-based medical codinginformation. The method further includes causing the clinic server totransmit the device-based medical coding information to a claimadjudication server.

An aspect of the disclosed embodiments includes a tangible,non-transitory computer-readable medium. The tangible, non-transitorycomputer-readable medium stores instructions that, when executed, causea processor to receive information from the medical device. Theinstructions further cause the processor to transmit thedevice-generated information to a clinic server. The instructionsfurther cause the processor to cause the clinic server to, using thedevice-generated information, determine device-based medical codinginformation. The instructions further cause the processor to cause theclinic server to transmit the device-based medical coding information toa claim adjudication server.

Other technical features may be readily apparent to one skilled in theart from the following figures, descriptions, and claims.

Another aspect of the disclosed embodiments includes a system thatincludes a processing device and a memory communicatively coupled to theprocessing device and capable of storing instructions. The processingdevice executes the instructions to perform any of the methods,operations, or steps described herein.

Another aspect of the disclosed embodiments includes a tangible,non-transitory computer-readable medium storing instructions that, whenexecuted, cause a processing device to perform any of the methods,operations, or steps disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is best understood from the following detaileddescription when read in conjunction with the accompanying drawings. Itis emphasized that, according to common practice, the various featuresof the drawings are not to-scale. On the contrary, the dimensions of thevarious features are arbitrarily expanded or reduced for clarity.

For a more complete understanding of this disclosure and its advantages,reference is now made to the following description, taken in conjunctionwith the accompanying drawings, in which:

FIG. 1 generally illustrates a component diagram of an illustrativemedical system according to the principles of the present disclosure;

FIG. 2 generally illustrates an example medical device according to theprinciples of the present disclosure;

FIG. 3 generally illustrates a component diagram of an illustrativeclinic server system according to the principles of the presentdisclosure;

FIG. 4 generally illustrates a component diagram and method of anillustrative medical claim processing system and information flowaccording to the principles of the present disclosure;

FIG. 5 generally illustrates a component diagram of an alternativearrangement of an illustrative medical claim processing system accordingto the principles of the present disclosure;

FIG. 6 generally illustrates a method of processing medical claims at aclinic server according to the principles of the present disclosure;

FIG. 7 generally illustrates a method of processing medical claims at amedical system according to the principles of the present disclosure;

FIG. 8 generally illustrates an example computer system according tocertain aspects of this disclosure;

FIG. 9 generally illustrates a perspective view of an embodiment of thedevice, such as a treatment device, according to certain aspects of thisdisclosure;

FIG. 10 generally illustrates a perspective view of a pedal of thetreatment device of FIG. 9 according to certain aspects of thisdisclosure; and

FIG. 11 generally illustrates a perspective view of a person using thetreatment device of FIG. 9 according to certain aspects of thisdisclosure.

NOTATION AND NOMENCLATURE

Various terms are used to refer to particular system components.Different companies may refer to a component by different names—thisdocument does not intend to distinguish between components that differin name but not function. In the following discussion and in the claims,the terms “including” and “comprising” are used in an open-endedfashion, and thus should be interpreted to mean “including, but notlimited to . . . . ” Also, the term “couple” or “couples” is intended tomean either an indirect or direct connection. Thus, if a first devicecouples to a second device, that connection may be through a directconnection or through an indirect connection via other devices andconnections.

The terminology used herein is for the purpose of describing particularexample embodiments only, and is not intended to be limiting. As usedherein, the singular forms “a,” “an,” and “the” may be intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. The method steps, processes, and operations described hereinare not to be construed as necessarily requiring their performance inthe particular order discussed or illustrated, unless specificallyidentified as an order of performance. It is also to be understood thatadditional or alternative steps may be employed.

The terms first, second, third, etc. may be used herein to describevarious elements, components, regions, layers and/or sections; however,these elements, components, regions, layers and/or sections should notbe limited by these terms. These terms may be only used to distinguishone element, component, region, layer, or section from another region,layer, or section. Terms such as “first,” “second,” and other numericalterms, when used herein, do not imply a sequence or order unless clearlyindicated by the context. Thus, a first element, component, region,layer, or section discussed below could be termed a second element,component, region, layer, or section without departing from theteachings of the example embodiments. The phrase “at least one of,” whenused with a list of items, means that different combinations of one ormore of the listed items may be used, and only one item in the list maybe needed. For example, “at least one of: A, B, and C” includes any ofthe following combinations: A, B, C, A and B, A and C, B and C, and Aand B and C. In another example, the phrase “one or more” when used witha list of items means there may be one item or any suitable number ofitems exceeding one.

Spatially relative terms, such as “inner,” “outer,” “beneath,” “below,”“lower,” “above,” “upper,” “top,” “bottom,” “inside,” “outside,”“contained within,” “superimposing upon,” and the like, may be usedherein. These spatially relative terms can be used for ease ofdescription to describe one element's or feature's relationship toanother element(s) or feature(s) as illustrated in the figures. Thespatially relative terms may also be intended to encompass differentorientations of the device in use, or operation, in addition to theorientation depicted in the figures. For example, if the device in thefigures is turned over, elements described as “below” or “beneath” otherelements or features would then be oriented “above” the other elementsor features. Thus, the example term “below” can encompass both anorientation of above and below. The device may be otherwise oriented(rotated 90 degrees or at other orientations) and the spatially relativedescriptions used herein interpreted accordingly.

A “treatment plan” may include one or more treatment protocols, and eachtreatment protocol includes one or more treatment sessions. Eachtreatment session comprises several session periods, with each sessionperiod including a particular exercise for treating the body part of thepatient. For example, a treatment plan for post-operative rehabilitationafter a knee surgery may include an initial treatment protocol withtwice daily stretching sessions for the first 3 days after surgery and amore intensive treatment protocol with active exercise sessionsperformed 4 times per day starting 4 days after surgery. A treatmentplan may also include information pertaining to a medical procedure toperform on the patient, a treatment protocol for the patient using atreatment device, a diet regimen for the patient, a medication regimenfor the patient, a sleep regimen for the patient, additional regimens,or some combination thereof.

The terms telemedicine, telehealth, telemed, teletherapeutic,telemedicine, remote medicine, etc. may be used interchangeably herein.

The term “optimal treatment plan” may refer to optimizing a treatmentplan based on a certain parameter or factors or combinations of morethan one parameter or factor, such as, but not limited to, a measure ofbenefit which one or more exercise regimens provide to users, one ormore probabilities of users complying with one or more exerciseregimens, an amount, quality or other measure of sleep associated withthe user, information pertaining to a diet of the user, informationpertaining to an eating schedule of the user, information pertaining toan age of the user, information pertaining to a sex of the user,information pertaining to a gender of the user, an indication of amental state of the user, information pertaining to a genetic conditionof the user, information pertaining to a disease state of the user, anindication of an energy level of the user, information pertaining to amicrobiome from one or more locations on or in the user (e.g., skin,scalp, digestive tract, vascular system, etc.), or some combinationthereof.

As used herein, the term healthcare provider may include a medicalprofessional (e.g., such as a doctor, a nurse, a therapist, and thelike), an exercise professional (e.g., such as a coach, a trainer, anutritionist, and the like), or another professional sharing at leastone of medical and exercise attributes (e.g., such as an exercisephysiologist, a physical therapist, an occupational therapist, and thelike). As used herein, and without limiting the foregoing, a “healthcareprovider” may be a human being, a robot, a virtual assistant, a virtualassistant in virtual and/or augmented reality, or an artificiallyintelligent entity, such entity including a software program, integratedsoftware and hardware, or hardware alone.

Real-time may refer to less than or equal to 2 seconds. Near real-timemay refer to any interaction of a sufficiently short time to enable twoindividuals to engage in a dialogue via such user interface, and willpreferably but not determinatively be less than 10 seconds (or anysuitably proximate difference between two different times) but greaterthan 2 seconds.

Any of the systems and methods described in this disclosure may be usedin connection with rehabilitation. Rehabilitation may be directed atcardiac rehabilitation, rehabilitation from stroke, multiple sclerosis,Parkinson's disease, myasthenia gravis, Alzheimer' s disease, any otherneurodegenative or neuromuscular disease, a brain injury, a spinal cordinjury, a spinal cord disease, a joint injury, a joint disease,post-surgical recovery, or the like. Rehabilitation can further involvemuscular contraction in order to improve blood flow and lymphatic flow,engage the brain and nervous system to control and affect a traumatizedarea to increase the speed of healing, reverse or reduce pain (includingarthralgias and myalgias), reverse or reduce stiffness, recover range ofmotion, encourage cardiovascular engagement to stimulate the release ofpain-blocking hormones or to encourage highly oxygenated blood flow toaid in an overall feeling of well-being. Rehabilitation may be providedfor individuals of average weight in reasonably good physical conditionhaving no substantial deformities, as well as for individuals moretypically in need of rehabilitation, such as those who are elderly,obese, subject to disease processes, injured and/or who have a severelylimited range of motion. Unless expressly stated otherwise, is to beunderstood that rehabilitation includes prehabilitation (also referredto as “pre-habilitation” or “prehab”). Prehabilitation may be used as apreventative procedure or as a pre-surgical or pre-treatment procedure.Prehabilitation may include any action performed by or on a patient (ordirected to be performed by or on a patient, including, withoutlimitation, remotely or distally through telemedicine) to, withoutlimitation, prevent or reduce a likelihood of injury (e.g., prior to theoccurrence of the injury); improve recovery time subsequent to surgery;improve strength subsequent to surgery; or any of the foregoing withrespect to any non-surgical clinical treatment plan to be undertaken forthe purpose of ameliorating or mitigating injury, dysfunction, or othernegative consequence of surgical or non-surgical treatment on anyexternal or internal part of a patient's body. For example, a mastectomymay require prehabilitation to strengthen muscles or muscle groupsaffected directly or indirectly by the mastectomy. As a furthernon-limiting example, the removal of an intestinal tumor, the repair ofa hernia, open-heart surgery or other procedures performed on internalorgans or structures, whether to repair those organs or structures, toexcise them or parts of them, to treat them, etc., can require cuttingthrough, dissecting and/or harming numerous muscles and muscle groups inor about, without limitation, the skull or face, the abdomen, the ribsand/or the thoracic cavity, as well as in or about all joints andappendages. Prehabilitation can improve a patient's speed of recovery,measure of quality of life, level of pain, etc. in all the foregoingprocedures. In one embodiment of prehabilitation, a pre-surgicalprocedure or a pre-non-surgical-treatment may include one or more setsof exercises for a patient to perform prior to such procedure ortreatment. Performance of the one or more sets of exercises may berequired in order to qualify for an elective surgery, such as a kneereplacement. The patient may prepare an area of his or her body for thesurgical procedure by performing the one or more sets of exercises,thereby strengthening muscle groups, improving existing muscle memory,reducing pain, reducing stiffness, establishing new muscle memory,enhancing mobility (i.e., improve range of motion), improving bloodflow, and/or the like.

The phrase, and all permutations of the phrase, “respective measure ofbenefit with which one or more exercise regimens may provide the user”(e.g., “measure of benefit,” “respective measures of benefit,” “measuresof benefit,” “measure of exercise regimen benefit,” “exercise regimenbenefit measurement,” etc.) may refer to one or more measures of benefitwith which one or more exercise regimens may provide the user.

DETAILED DESCRIPTION

The following discussion is directed to various embodiments of thepresent disclosure. Although one or more of these embodiments may bepreferred, the embodiments disclosed should not be interpreted, orotherwise used, as limiting the scope of the disclosure, including theclaims. In addition, one skilled in the art will understand that thefollowing description has broad application, and the discussion of anyembodiment is meant only to be exemplary of that embodiment, and notintended to intimate that the scope of the disclosure, including theclaims, is limited to that embodiment.

Determining optimal remote examination procedures to create an optimaltreatment plan for a patient having certain characteristics (e.g.,vital-sign or other measurements; performance; demographic;psychographic; geographic; diagnostic; measurement- or test-based;medically historic; behavioral historic; cognitive; etiologic;cohort-associative; differentially diagnostic; surgical, physicallytherapeutic, pharmacologic and other treatment(s) recommended; etc.) maybe a technically challenging problem. For example, a multitude ofinformation may be considered when determining a treatment plan, whichmay result in inefficiencies and inaccuracies in the treatment planselection process. In a rehabilitative setting, some of the multitude ofinformation considered may include characteristics of the patient suchas personal information, performance information, and measurementinformation. The personal information may include, e.g., demographic,psychographic or other information, such as an age, a weight, a gender,a height, a body mass index, a medical condition, a familial medicationhistory, an injury, a medical procedure, a medication prescribed, orsome combination thereof. The performance information may include, e.g.,an elapsed time of using a treatment device, an amount of force exertedon a portion of the treatment device, a range of motion achieved on thetreatment device, a movement speed of a portion of the treatment device,a duration of use of the treatment device, an indication of a pluralityof pain levels using the treatment device, or some combination thereof.The measurement information may include, e.g., a vital sign, arespiration rate, a heartrate, a temperature, a blood pressure, aglucose level or other biomarker, or some combination thereof. It may bedesirable to process and analyze the characteristics of a multitude ofpatients, the treatment plans performed for those patients, and theresults of the treatment plans for those patients.

Further, another technical problem may involve distally treating, via acomputing device during a telemedicine session, a patient from alocation different than a location at which the patient is located. Anadditional technical problem is controlling or enabling, from thedifferent location, the control of a treatment device used by thepatient at the patient's location. Oftentimes, when a patient undergoesrehabilitative surgery (e.g., knee surgery), a medical professional mayprescribe a treatment device to the patient to use to perform atreatment protocol at their residence or at any mobile location ortemporary domicile. A medical professional may refer to a doctor,physician assistant, nurse, chiropractor, dentist, physical therapist,acupuncturist, physical trainer, or the like. A medical professional mayrefer to any person with a credential, license, degree, or the like inthe field of medicine, physical therapy, rehabilitation, or the like.

When the healthcare provider is located in a location different from thepatient and the treatment device, it may be technically challenging forthe healthcare provider to monitor the patient's actual progress (asopposed to relying on the patient's word about their progress) in usingthe treatment device, modify the treatment plan according to thepatient's progress, adapt the treatment device to the personalcharacteristics of the patient as the patient performs the treatmentplan, and the like.

Further, in addition to the information described above, determiningoptimal examination procedures for a particular ailment (e.g., injury,disease, any applicable medical condition, etc.) may include physicallyexamining the injured body part of a patient. The healthcare provider,such as a physician or a physical therapist, may visually inspect theinjured body part (e.g., a knee joint). The inspection may includelooking for signs of inflammation or injury (e.g., swelling, redness,and warmth), deformity (e.g., symmetrical joints and abnormal contoursand/or appearance), or any other suitable observation. To determinelimitations of the injured body part, the healthcare provider mayobserve the injured body part as the patient attempts to perform normalactivity (e.g., bending and extending the knee and gauging anylimitations to the range of motion of the injured knee). The healthcareprovide may use one or more hands and/or fingers to touch the injuredbody part. By applying pressure to the injured body part, the healthcareprovider can obtain information pertaining to the extent of the injury.For example, the healthcare provider's fingers may palpate the injuredbody part to determine if there is point tenderness, warmth, weakness,strength, or to make any other suitable observation.

It may be desirable to compare characteristics of the injured body partwith characteristics of a corresponding non-injured body part todetermine what an optimal treatment plan for the patient may be suchthat the patient can obtain a desired result. Thus, the healthcareprovider may examine a corresponding non-injured body part of thepatient. For example, the healthcare provider's fingers may palpate anon-injured body part (e.g., a left knee) to determine a baseline of howthe patient's non-injured body part feels and functions. The healthcareprovider may use the results of the examination of the non-injured bodypart to determine the extent of the injury to the corresponding injuredbody part (e.g., a right knee). Additionally, injured body parts mayaffect other body parts (e.g., a knee injury may limit the use of theaffected leg, leading to atrophy of leg muscles). Thus, the healthcareprovider may also examine additional body parts of the patient forevidence of atrophy of or injury to surrounding ligaments, tendons,bones, and muscles, examples of muscles being such as quadriceps,hamstrings, or calf muscle groups of the leg with the knee injury. Thehealthcare provider may also obtain information as to a pain level ofthe patient before, during, and/or after the examination.

The healthcare provider can use the information obtained from theexamination (e.g., the results of the examination) to determine a propertreatment plan for the patient. If the healthcare provider cannotconduct a physical examination of the one or more body parts of thepatient, the healthcare provider may not be able to fully assess thepatient's injury and the treatment plan may not be optimal. Accordingly,embodiments of the present disclosure pertain to systems and methods forconducting a remote examination of a patient. The remote examinationsystem provides the healthcare provider with the ability to conduct aremote examination of the patient, not only by communicating with thepatient, but by virtually observing and/or feeling the patient's one ormore body parts.

In some embodiments, the systems and methods described herein may beconfigured for manipulation of a medical device. For example, thesystems and methods may be configured to use a medical device configuredto be manipulated by an individual while the individual is performing atreatment plan. The individual may include a user, patient, or other aperson using the treatment device to perform various exercises forprehabilitation, rehabilitation, stretch training, e.g., pliability,medical procedures, and the like. The systems and methods describedherein may be configured to use and/or provide a patient interfacecomprising an output device, wherein the output device is configured topresent telemedicine information associated with a telemedicine session.

In some embodiments, the systems and methods described herein may beconfigured for processing medical claims. For example, the systemincludes a processor configured to receive device-generated informationfrom a medical device. Using the device-generated information received,the processor is configured to determine device-based medical codinginformation. The processor is further configured to transmit thedevice-based medical coding information to a claim adjudication server.Any or all of the methods described may be implemented during atelemedicine session or at any other desired time.

In some embodiments, the medical claims may be processed, during atelemedicine or telehealth session, by a healthcare provider. Thehealthcare provider may select a particular treatment plan for thepatient to cause that treatment plan to be transmitted to the patientand/or to control, based on the treatment plan, the treatment device. Insome embodiments, to facilitate telehealth or telemedicine applications,including remote diagnoses, determination of treatment plans andrehabilitative and/or pharmacologic prescriptions, the artificialintelligence engine may receive data, instructions, or the like and/oroperate distally from the patient and the treatment device.

In such cases, the recommended treatment plans and/or excluded treatmentplans may be presented simultaneously with a video of the patient inreal-time or near real-time during a telemedicine or telehealth sessionon a user interface of a computing device of a medical professional. Thevideo may also be accompanied by audio, text and other multimediainformation and/or other sensorial or perceptive (e.g., tactile,gustatory, haptic, pressure-sensing-based or electromagnetic (e.g.,neurostimulation), and without limitation, gesture recognition, gesturecontrol, touchless user interfaces (TUIs), kinetic user interfaces(KUIs), tangible user interfaces, wired gloves, depth-aware cameras,stereo cameras, and gesture-based controllers. Real-time may refer toless than or equal to 2 seconds. Near real-time may refer to anyinteraction of a sufficiently short time to enable two individuals toengage in a dialogue via such user interface, and will generally be lessthan 10 seconds (or any suitably proximate difference between twodifferent times) but greater than 2 seconds.

FIGS. 1-11, discussed below, and the various embodiments used todescribe the principles of this disclosure are by way of illustrationonly and should not be construed in any way to limit the scope of thedisclosure.

FIG. 1 illustrates a component diagram of an illustrative medical system100 in accordance with aspects of this disclosure. The medical system100 may include a medical device 102. The medical device 102 may be atesting device, a diagnostic device, a therapeutic device, or any othersuitable medical device. “Medical device” as used in this context meansany hardware, software, mechanical or other device, such as a treatmentdevice (e.g., medical device 102, treatment device 10, or the like),that may assist in a medical service, regardless of whether it is FDA(or other governmental regulatory body of any given country) approved,required to be FDA (or other governmental regulatory body of any givencountry) approved or available commercially or to consumers without suchapproval. Non-limiting examples of medical devices include athermometer, an MRI machine, a CT-scan machine, a glucose meter, anapheresis machine, and a physical therapy machine such as a physicaltherapy cycle. Non-limiting examples of places where the medical device102 may be located include a healthcare clinic, a physicalrehabilitation center, and a user's home to allow for telemedicinetreatment, rehabilitation, and/or testing. FIG. 2 illustrates an exampleof the medical device 102 where the medical device 102 is a physicaltherapy cycle.

As generally illustrated in FIG. 2, the medical device 102 may comprisean electromechanical device, such as a physical therapy device. FIG. 2generally illustrates a perspective view of an example of a medicaldevice 102 according to certain aspects of this disclosure.Specifically, the medical device 102 illustrated is an electromechanicaldevice 202, such as an exercise and rehabilitation device (e.g., aphysical therapy device or the like). The electromechanical device 202is shown having pedal 210 on opposite sides that are adjustablypositionable relative to one another on respective radially-adjustablecouplings 208. The depicted electromechanical device 202 is configuredas a small and portable unit so that it is easily transported todifferent locations at which rehabilitation or treatment is to beprovided, such as at patients' homes, alternative care facilities, orthe like. The patient may sit in a chair proximate the electromechanicaldevice 202 to engage the electromechanical device 202 with the patient'sfeet, for example. The electromechanical device 202 includes a rotarydevice such as radially-adjustable couplings 208 or flywheel or the likerotatably mounted such as by a central hub to a frame or other support.The pedals 210 are configured for interacting with a patient to berehabilitated and may be configured for use with lower body extremitiessuch as the feet, legs, or upper body extremities, such as the hands,arms, and the like. For example, the pedal 210 may be a bicycle pedal ofthe type having a foot support rotatably mounted onto an axle withbearings. The axle may or may not have exposed end threads for engaginga mount on the radially-adjustable coupling 208 to locate the pedal onthe radially-adjustable coupling 208. The radially-adjustable coupling208 may include an actuator configured to radially adjust the locationof the pedal to various positions on the radially-adjustable coupling208.

Alternatively, the radially-adjustable coupling 208 may be configured tohave both pedals 210 on opposite sides of a single coupling 208. In someembodiments, as depicted, a pair of radially-adjustable couplings 208may be spaced apart from one another but interconnected to an electricmotor 206. In the depicted example, the computing device 104 may bemounted on the frame of the electromechanical device 202 and may bedetachable and held by the user while the user operates theelectromechanical device 202. The computing device 104 may present thepatient portal 212 and control the operation of the electric motor 206,as described herein.

In some embodiments, as described in U.S. Pat. No. 10,173,094 (U.S.application Ser. No. 15/700,293), which is incorporated by referenceherein in its entirety for all purposes, the medical device 102 may takethe form of a traditional exercise/rehabilitation device which is moreor less non-portable and remains in a fixed location, such as arehabilitation clinic or medical practice. The medical device 102 mayinclude a seat and is less portable than the medical device 102 shown inFIG. 2. FIG. 2 is not intended to be limiting: the electromechanicaldevice 202 may include more or fewer components than those illustratedin FIG. 2.

FIGS. 9-10 generally illustrate an embodiment of a treatment device,such as a treatment device 10. More specifically, FIG. 9 generallyillustrates a treatment device 10 in the form of an electromechanicaldevice, such as a stationary cycling machine 14, which may be called astationary bike, for short. The stationary cycling machine 14 includes aset of pedals 12 each attached to a pedal arm 20 for rotation about anaxle 16. In some embodiments, and as generally illustrated in FIG. 10,the pedals 12 are movable on the pedal arm 20 in order to adjust a rangeof motion used by the patient in pedaling. For example, the pedals beinglocated inwardly toward the axle 16 corresponds to a smaller range ofmotion than when the pedals are located outwardly away from the axle 16.A pressure sensor 18 is attached to or embedded within one of the pedals12 for measuring an amount of force applied by the patient on the pedal102. The pressure sensor 18 may communicate wirelessly to the treatmentdevice 10 and/or to the patient interface 26. FIGS. 9-10 are notintended to be limiting: the treatment device 10 may include more orfewer components than those illustrated in FIGS. 9-10.

FIG. 11 generally illustrates a person (a patient) using the treatmentdevice 10 of FIG. 9, and showing sensors and various data parametersconnected to a patient interface 26. The example patient interface 26 isa tablet computer or smartphone, or a phablet, such as an iPad, aniPhone, an Android device, or a Surface tablet, which is held manuallyby the patient. In some other embodiments, the patient interface 26 maybe embedded within or attached to the treatment device 10. FIG. 11generally illustrates the patient wearing the ambulation sensor 22 onhis wrist, with a note showing “STEPS TODAY 1355”, indicating that theambulation sensor 22 has recorded and transmitted that step count to thepatient interface 26. FIG. 11 also generally illustrates the patientwearing the goniometer 24 on his right knee, with a note showing “KNEEANGLE 72°”, indicating that the goniometer 24 is measuring andtransmitting that knee angle to the patient interface 26. FIG. 11generally illustrates a right side of one of the pedals 12 with apressure sensor 18 showing “FORCE 12.5 lbs.”, indicating that the rightpedal pressure sensor 18 is measuring and transmitting that forcemeasurement to the patient interface 26. FIG. 11 also generallyillustrates a left side of one of the pedals 12 with a pressure sensor18 showing “FORCE 27 lbs.”, indicating that the left pedal pressuresensor 18 is measuring and transmitting that force measurement to thepatient interface 26. FIG. 11 also generally illustrates other patientdata, such as an indicator of “SESSION TIME 0:04:13”, indicating thatthe patient has been using the treatment device 10 for 4 minutes and 13seconds. This session time may be determined by the patient interface 26based on information received from the treatment device 10. FIG. 11 alsogenerally illustrates an indicator showing “PAIN LEVEL 3”, Such a painlevel may be obtained from the patient in response to a solicitation,such as a question, presented upon the patient interface 26.

The medical device 102 may include, be coupled to, or be incommunication with a computing device 104. The computing device 104 mayinclude a processor 106. The processor 106 can include, for example,computers, intellectual property (IP) cores, application-specificintegrated circuits (ASICs), programmable logic arrays, opticalprocessors, programmable logic controllers, microcode, microcontrollers,servers, microprocessors, digital signal processors, any other suitablecircuit, or any combination thereof

The computing device 104 may include a memory device 108 incommunication with the processor 106. The memory device 108 can includeany type of memory capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, aflash drive, a compact disc (CD), a digital video disc (DVD), a solidstate drive (SSD), or any other suitable type of memory.

The computing device 104 may include an input device 110 incommunication with the processor 106. Examples of the input device 110include a keyboard, a keypad, a mouse, a microphone supported byspeech-to-text software, or any other suitable input device. The inputdevice 110 may be used by a medical system operator to inputinformation, such as user identifying information, observational notes,or any other suitable information. An operator is to be understoodthroughout this disclosure to include both people and computer software,such as programs or artificial intelligence.

The computing device 104 may include an output device 112 incommunication with the processor 106. The output device 112 may be usedto provide information to the medical device operator or a user of themedical device 102. Examples of the output device 112 include a displayscreen, a speaker, an alarm system, or any other suitable output device,including haptic, tactile, olfactory, or gustatory ones, and withoutlimitation, gesture recognition, gesture control, touchless userinterfaces (TUIs), kinetic user interfaces (KUIs), tangible userinterfaces, wired gloves, depth-aware cameras, stereo cameras, andgesture-based controllers. In some embodiments, such as where thecomputing device 104 includes a touchscreen, the input device 110 andthe output device 112 may be the same device.

For communicating with remote computers and servers, the computingdevice 104 may include a network adapter 114 in communication with theprocessor 106. The network adapter 114 may include wired or wirelessnetwork adapter devices or a wired network port.

Any time information is transmitted or communicated, the information maybe in EDI file format or any other suitable file format. In any of themethods or steps of the method, file format conversions may take place.By utilizing Internet of Things (IoT) gateways, data streams, ETLbucketing, EDI mastering, or any other suitable technique, data can bemapped, converted, or transformed into a carrier preferred state. As aresult of the volume of data being transmitted, the data securityrequirements, and the data consistency requirements, enterprise gradearchitecture may be utilized for reliable data transfer.

FIG. 1 is not intended to be limiting; the medical system 100 and thecomputing device 104 may include more or fewer components than thoseillustrated in FIG. 1.

FIG. 3 illustrates a component diagram of an illustrative clinic serversystem 300 in accordance with aspects of this disclosure. The clinicserver system 300 may include a clinic server 302. The clinic serversystem 300 or clinic server 302 may be servers owned or controlled by amedical clinic (such as a doctor's office, testing site, or therapyclinic) or by a medical practice group (such as a testing company,outpatient procedure clinic, diagnostic company, or hospital). Theclinic server 302 may be proximate to the medical system 100. In otherembodiments, the clinic server 302 may be remote from the medical system100. For example, during telemedicine-based or telemedicine-mediatedtreatment, rehabilitation, or testing, the clinic server 302 may belocated at a healthcare clinic and the medical system 100 may be locatedat a patient's home. The clinic server 302 may be a rackmount server, arouter computer, a personal computer, a portable digital assistant, asmartphone, a laptop computer, a tablet computer, a netbook, a desktopcomputer, any other suitable computing device, or any combination of theabove. The clinic server 302 may be cloud-based or be a real-timesoftware platform, and it may include privacy (e.g., anonymization,pseudonymization, or other) software or protocols, and/or includesecurity software or protocols. The clinic server 302 may include acomputing device 304. The computing device 304 may include a processor306. The processor 306 can include, for example, computers, intellectualproperty (IP) cores, application-specific integrated circuits (ASICs),programmable logic arrays, optical processors, programmable logiccontrollers, microcode, microcontrollers, servers, microprocessors,digital signal processors, any other suitable circuit, or anycombination thereof.

The computing device 304 may include a memory device 308 incommunication with the processor 306. The memory device 308 can includeany type of memory capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, aflash drive, a compact disc (CD), a digital video disc (DVD), a solidstate drive (SSD), or any other suitable type of memory.

The computing device 304 may include an input device 310 incommunication with the processor 306. Examples of the input device 310include a keyboard, a keypad, a mouse, a microphone supported byspeech-to-text software, or any other suitable input device.

The computing device 304 may include an output device 312 incommunication with the processor 106. Examples of the output device 312include a display screen, a speaker, or any other suitable outputdevice, including haptic, tactile, olfactory, or gustatory ones, andwithout limitation, gesture recognition, gesture control, touchless userinterfaces (TUIs), kinetic user interfaces (KUIs), tangible userinterfaces, wired gloves, depth-aware cameras, stereo cameras, andgesture-based controllers. In some embodiments, such as where thecomputing device 304 includes a touchscreen, the input device 310 andthe output device 312 may be the same device.

The computing device 304 may include a network adapter 314 incommunication with the processor 306 for communicating with remotecomputers and/or servers. The network adapter 314 may include wired orwireless network adapter devices.

FIG. 3 is not intended to be limiting; the clinic server system 300, theclinic server 302, and the computing device 304 may include more orfewer components than those illustrated in FIG. 3.

FIG. 4 illustrates a component diagram and method of an illustrativemedical claim processing system 400 and information flow according toaspects of this disclosure. The medical claim processing system 400 mayinclude the medical system 100. The medical claim processing system 400may include a clinic server 302.

The medical claim processing system 400 may include a patient notesdatabase 402. The medical claim processing system 400 may include anelectronic medical records (EMR) database 404. One or both of thepatient notes database 402 and the EMR database 404 may be located onthe clinic server 302, on one or more remote servers, or on any othersuitable system or server.

The medical claim processing system 400 may include a biller server 406.The biller server 406 may be owned or controlled by a medical practicegroup (such as a testing company, outpatient procedure clinic,diagnostic company, or a hospital), a health insurance company, agovernmental entity, or any other organization (including third-partyorganizations) associated with medical billing procedures. The billerserver 406 may be a rackmount server, a router computer, a personalcomputer, a portable digital assistant, a smartphone, a laptop computer,a tablet computer, a netbook, a desktop computer, any other suitablecomputing device, or any combination of the above. The biller server 406may be cloud-based or be a real-time software platform, and it mayinclude privacy (e.g., anonymization, pseudonymization, or other)software or protocols, and/or include security software or protocols.The biller server 406 may contain a computing device including anycombination of the components of the computing device 304 as illustratedin FIG. 3. The biller server 406 may be proximate to or remote from theclinic server 302.

The medical claim processing system 400 may include a claim adjudicationserver 408. The claim adjudication server 408 may be owned or controlledby a health insurance company, governmental entity, or any otherorganization (including third-party organizations) associated withmedical billing procedures. The claim adjudication server 408 may be arackmount server, a router computer, a personal computer, a portabledigital assistant, a smartphone, a laptop computer, a tablet computer, anetbook, a desktop computer, any other suitable computing device, or anycombination of the above. The claim adjudication server 408 may becloud-based or be a real-time software platform, and it may includeprivacy (e.g., anonymization, pseudonymization, or other) software orprotocols, and/or include security software or protocols. The claimadjudication server 408 may contain a computing device including anycombination of the components of the computing device 304 as illustratedin FIG. 3. The claim adjudication server 408 may be proximate to orremote from the biller server 406. The claim adjudication server 408 maybe configured to make or receive a determination about whether a claimshould be paid.

At step 410, device-generated information may be transmitted from themedical system 100 to the clinic server 302. The device-generatedinformation may include medical result information generated by themedical device 102. Medical result information can include informationpertaining to a patient's medical condition and can include, withoutlimitation, medical test results. Such medical test results can include,without limitation, CT scans, X-ray images, blood test results, and/orbiopsy results. For example, the CT scans may include medical resultinformation pertaining to a patient's medical condition.

The device-generated information may include medical coding informationgenerated by the medical device 102. Medical coding information refers,without limitation, to medical information represented by a code, suchas a DRG, an ICD-10 code, or other codes embodying, representing, orencoding information related to a medical procedure or a medical test.Medical coding information can be device-based. Such device-basedmedical coding information (e.g., an ICD-10 code) can be derived fromdevice-generated information (e.g., a CT scan), produced by, orotherwise sourced from a medical device (e.g., CT machine) or actionsperformed by, with, or on a medical device (e.g., rehabilitation on aphysical therapy cycle). Device-based medical coding information can beused to supplement and/or replace medical coding information fromalternative sources (e.g., remote databases, billing agencies, etc.). Inan example where telemedicine is used to facilitate or mediate bloodglucose testing on a patient using a glucose meter located at thepatient's home or carried by the patient, device-generated informationmay include medical coding information (e.g., an ICD-10 code) indicatingthat a procedure, such as a blood glucose test, was performed by using aglucose meter and that the glucose meter generated blood glucose testresults. In this example, the glucose meter (a medical device) producesdevice-generated information when it produces the blood glucose testresults and when it generates the medical coding information. Themedical system 100 and the clinic server 302 may be communicativelycoupled via the network adapter 114. The device-generated informationmay be transmitted from the medical system 100 to the clinic server 302via, for example, the network adapter 114.

At step 412, clinic server information may be transmitted from clinicserver 302 to the patient notes database 402. The clinic serverinformation may include medical result information generated by themedical device 102. Using the device-generated information received fromthe medical device 10, the clinic server information may includedevice-based medical result information determined by the clinic server302. The clinic server information may include medical codinginformation generated by the medical device 102. Using thedevice-generated information received from the medical device 102, theclinic server information may include device-based medical codinginformation determined by the clinic server 302, including a DRG, anICD-10, or another code generated by the medical device 102 anddetermined to be valid by the clinic server 302. The clinic serverinformation may include an ICD-10 code that is determined using ananalysis of the device-generated information. An example of determiningthe ICD-10 code using the analysis of the device-generated informationincludes the following: 1) the clinic server 302 identifies the imagefrom the MRI scan as being an MM scan of an upper spine of a patient,and 2) the clinic server 302 determines the ICD-10 code associated withthe MM scan of the upper spine. A clinic operator may also enteradditional information into the patient notes database 402. For example,a doctor may enter additional medical result information and additionalmedical coding information into the patient notes database 402.

At step 414, patient notes information may be transmitted from thepatient notes database 402 to the EMR database 404. The patient notesinformation may include medical result information generated by themedical device 102. Using the device-generated information received fromthe medical device 102, the patient notes information may includedevice-based medical result information determined by the clinic server302. The patient notes information may include reviewed medical codinginformation (i.e., medical coding information that has been reviewedand/or input by a clinic operator). The patient notes information mayinclude additional medical coding or result information entered by theclinic operator. A clinic operator may make a decision about whatpatient notes information should be or is transmitted from the from thepatient notes database 402 to the EMR database 404. For example, aclinic operator may determine that it is not necessary to transmit aportion of the medical result information generated by the medicaldevice 102, as, e.g., that information could be test data that does notreflect factual medical results of tests performed on a patient.

At step 416, EMR information may be transmitted from the EMR database404 to the biller server 406. The EMR information may include medicalresult information generated by the medical device 102. Using thedevice-generated information received from the medical device 102, theEMR information may include device-based medical result informationdetermined by the clinic server 302. The EMR information may includereviewed medical coding information. The EMR information may includeadditional medical result information entered by the clinic operator.The EMR information may include additional medical coding informationentered by the clinic operator. A clinic operator may make a decisionabout which EMR information is transmitted from the EMR database 404 tothe biller server 406. For example, a clinic operator may determine thatit is not necessary to transmit a portion of the medical resultinformation generated by the medical device 102, as, e.g., thatinformation may be test data that does not reflect factual medicalresults of tests performed on a patient. A biller operator may enterbiller notes into the biller server 406.

At step 418, biller information may be transmitted from the billerserver 406 to the claim adjudication server 408. The biller informationmay include medical result information generated by the medical device102. Using the device-generated information received from the medicaldevice 102, the biller information may include device-based medicalresult information determined by the clinic server 302. The billerinformation may include reviewed medical coding information. The billerinformation may include additional medical result information entered bythe clinic operator. The biller information may include additionalmedical coding information entered by the clinic operator. The billerinformation may include biller notes entered by the biller operator. Forexample, a biller operator may enter biller notes to pay in full, pay areduced amount, reject the bill, or add any other suitable note. Abiller operator may make a decision about which biller information istransmitted from the biller server 406 to the claim adjudication server408. For example, the biller operator may determine that certain billerinformation is suspect and requires additional review, flag that billerinformation for review, and not send that information to claimadjudication.

At step 420, clinic server information may be transmitted from theclinic server 302 to the EMR database 404. The clinic server informationmay include medical result information generated by the medical device102. Using the device-generated information received from the medicaldevice 102, the clinic server information may include device-basedmedical result information determined by the clinic server 302. Theclinic server information may include medical coding informationgenerated by the medical device 102. Using the device-generatedinformation received from the medical device 102, the clinic serverinformation may include device-based medical coding informationdetermined by the clinic server 302. Bypassing the patient notesdatabase 402 may allow for unmodified clinic server information to beentered into the electronic medical records.

At step 422, information may be transmitted from the EMR database 404 tothe clinic server 302. The information may include additional medicalresult or coding information entered by the clinic operator. Theinformation may include reviewed medical coding information approved ormodified by the clinic operator. The clinic server 302 maycross-reference the medical coding information that was sent by theclinic server 302 and the information that was received by the clinicserver 302. The clinic server 302 may determine whether the medicalcoding information received by the clinic server 302 can be reconciledwith the medical coding information sent by the clinic server 302. Inthe context of this application, “reconciled” or “reconcilable” meansthat the medical coding information received by the clinic server 302and the medical coding information sent by the clinic server 302 are notcontradictory. For instance, if a knee injury is indicated, but an elbowsurgery is performed, the two are not reconcilable. However, if an elbowinjury is indicated, and an elbow surgery is performed, the two arereconcilable.

At step 424, information may be transmitted from the clinic server 302to the claim adjudication server 408. The information may includemedical result information generated by the medical device 102. Usingthe device-generated information received from the medical device 102,the information may include device-based medical result informationdetermined by the clinic server 302. The information may include medicalcoding information generated by the medical device 102. Using thedevice-generated information received from the medical device 102, theinformation may include device-based medical coding informationdetermined by the clinic server 302. The information may includeadditional medical result and coding information entered by the clinicoperator. The information may include reviewed medical codinginformation. The information may include the determination about whetherthe medical coding information received by the clinic server 302 can bereconciled with the medical coding information sent by the clinic server302. By transmitting the device-based medical coding informationdirectly to the claim adjudication server 408, fewer total data packetsmay be transmitted, reducing total processor and network loads. This isas compared to current systems, where all medical coding information istransmitted a multitude of times: through, inter alia, patient notesdatabases 402, EMR databases 404, biller servers 406, and finally claimadjudication servers 408.

FIG. 4 is not intended to be limiting; medical claim processing system400 and any sub-components thereof may include more or fewer components,steps, and/or processes than those illustrated in FIG. 4. Any or all ofthe methods described may be implemented during a telemedicine sessionor at any other desired time.

FIG. 5 illustrates a component diagram of an illustrative medical claimprocessing system 500 according to aspects of this disclosure. Themedical claim processing system 500 can include the medical system 100of FIG. 1. The medical system 100 may be in communication with a network502. The network 502 may be a public network (e.g., connected to theInternet via wired (Ethernet) or wireless (Wi-Fi)), a private network(e.g., a local area network (LAN) or wide area network (WAN)), acombination thereof, or any other suitable network.

The medical claim processing system 500 can include the clinic server302 of FIG. 3. The clinic server 302 may be in communication with thenetwork 502.

The medical claim processing system 500 can include a cloud-basedlearning system 504. The cloud-based learning system 504 may be incommunication with the network 502. The cloud-based learning system 504may include one or more training servers 506 and form a distributedcomputing architecture. Each of the training servers 506 may include acomputing device, including any combination of one or more of thecomponents of the computing device 304 as illustrated in FIG. 3, or anyother suitable components. The training servers 506 may be incommunication with one another via any suitable communication protocol.The training servers 506 may store profiles for users including, but notlimited to, patients, clinics, practice groups, and/or insurers. Theprofiles may include information such as historical device-generatedinformation, historical device-based medical coding information,historical reviewed medical coding information, historicalcomputer-based determinations on whether the reviewed medical codinginformation can be reconciled with the device-based coding information,and historical human-based determinations on whether the reviewedmedical coding information has been reconciled with the device-basedcoding information. Other non-limiting examples of desired historicalinformation can include any information relating to a specific patient,condition, or population that was recorded at a time prior to theinteraction being billed as the medical claim.

In some aspects, the cloud-based learning system 504 may include atraining engine 508 capable of generating one or more machine learningmodels 510. The machine learning models 510 may be trained to generate“determination” algorithms that, using the device-generated information,aid in determining device-based medical coding information. Forinstance, if the medical device 102 is an MM, the machine learningmodels 510 may generate progressively more accurate algorithms todetermine, using device-generated information such as MRI images, whichtype of MM was performed and which type of medical coding information toassociate with the type of MM performed. To generate the one or moremachine learning models 510, the training engine 508 may train the oneor more machine learning models 510. The training engine 508 may use abase data set of historical device-generated information, historicaldevice-based medical coding information, historical reviewed medicalcoding information, any other desired historical information and/orhistorical computer-based or human-based determinations on whether thereviewed medical coding information can be reconciled with thedevice-based coding information. The training engine 508 may be arackmount server, a router computer, a personal computer, a portabledigital assistant, a smartphone, a laptop computer, a tablet computer, anetbook, a desktop computer, an Internet of Things (IoT) node or sensor,any other suitable computing device, or any combination of the above.The training engine 508 may be cloud-based or be a real-time softwareplatform, include privacy-enhancing, privacy-preserving or privacymodifying software or protocols, and/or include security software orprotocols. Using training data that includes training inputs andcorresponding target outputs, the one or more machine learning models510 may refer to model artifacts created by the training engine 508. Thetraining engine 508 may find patterns in the training data that map thetraining input to the target output and generate the machine learningmodels 510 that identify, store, or use these patterns. Althoughdepicted separately from the medical system 100, the clinic server 302,the biller server 406, the claim adjudication server 408, the trainingengine 508, and the machine learning models 510 may reside on themedical system 100. Alternatively, the clinic server 302, the billerserver 406, the claim adjudication server 408, the training engine 508,and the machine learning models 510 may reside on the clinic server 302,the biller server 406, the claim adjudication server 408, and/or anyother suitable server.

The machine learning models 510 may include one or more neural networks,such as an image classifier, a recurrent neural network, a convolutionalnetwork, a generative adversarial network, a fully connected neuralnetwork, any other suitable network, or any combination thereof. In someembodiments, the machine learning models 510 may be composed of a singlelevel of linear or non-linear operations or may include multiple levelsof non-linear operations. For example, the machine learning models 510may include numerous layers and/or hidden layers that performcalculations (e.g., dot products) using various neural nodes.

FIG. 5 is not intended to be limiting; the medical claim processingsystem 500, the medical system 100, the computing device 104, the clinicserver 302, the clinic server 302, the computing device 304, thecloud-based learning system 504, and any sub-components thereof mayinclude more or fewer components than those illustrated in FIG. 5. Anyor all of the methods described may be implemented during a telemedicinesession or at any other desired time.

FIG. 6 illustrates a computer-implemented method 600 for a clinic server302 processing medical claims. The method 600 may be implemented on asystem including a processor, such as the processor 306, and a memorydevice, such as the memory device 308. The method 600 may be implementedon a processor configured to perform the steps of the method 600. Themethod 600 may be implemented on the clinic server system 300. Themethod 600 may include operations implemented in computer instructionsstored in a memory device, such as the memory device 308, and executedby a processor, such as the processor 306, of a computing device, suchas the computing device 304. The steps of the method 600 may be storedin a non-transient computer-readable storage medium.

At step 602, the method 600 can include receiving device-generatedinformation from a medical device. The medical device may include themedical device 102 and/or the medical system 100. The device-generatedinformation may include medical coding and/or medical resultinformation.

At step 604, the method 600 can include, using the device-generatedinformation, determining device-based medical coding information. Thisdetermination can include cross-referencing information about actionsperformed by the medical device 102 with a reference list associatingthose actions with certain medical codes. The reference list could bestored on the clinic server 302, the cloud-based learning system 504, oron any other suitable server, database, or system. Furthermore, thisdetermination can include identifying a portion of the device-generatedinformation containing medical coding information.

At step 606, the method 600 can include, using the information,determining device-based medical result information. This determinationcan include determining that the device-generated information includestest results (e.g., a blood glucose measurement, a cholesterolmeasurement, etc.), medical imaging data (e.g., an X-Ray image, an MRIimage, etc.), or physical therapy (or rehabilitation) measurements(e.g., heart-rate, oxygen content, etc.).

At step 608, the method 600 can include transmitting the device-basedmedical result information to a patient notes database. The patientnotes database can include the patient notes database 402.

At step 610, the method 600 can include transmitting the device-basedmedical coding information to the EMR database. The EMR database caninclude the EMR database 404.

At step 612, the method 600 can include receiving reviewed medicalcoding information from the EMR database. The EMR database can includethe EMR database 404.

At step 614, the method 600 can include, using the reviewed medicalcoding information and the device-based medical coding information,determining a match indicator. The match indicator indicates whether thereviewed medical coding information can be reconciled with thedevice-based medical coding information. This determination can includecross-referencing the reviewed medical coding information with thedevice-based medical coding information to generate the match indicator.For example, both the reviewed medical coding information and thedevice-based medical coding information may be cross-referenced with adatabase to determine which reviewed medical coding information is andis not reconcilable with the device-based medical coding information.For instance, device-based medical coding information for a CT scan of aknee may be reconcilable with reviewed medical coding information of apatient being fitted for a knee brace, but not reconcilable withreviewed medical coding information of a patient being fitted for anelbow brace.

At step 616, the method 600 can include transmitting the device-basedmedical coding information directly to a claim adjudication server whilebypassing the EMR database 404 and the biller server 406. The claimadjudication server may be the claim adjudication server 408. Bytransmitting the device-based medical coding information directly to theclaim adjudication server 408, fewer total data packets may be sent,reducing network loads.

At step 618, the method 600 can include transmitting the determinationof whether the reviewed medical coding information can be reconciledwith the device-based medical coding information. The determination maybe transmitted to the claim adjudication server 408. The determinationmay be transmitted to the biller server. The biller server may be thebiller server 406. The determination may be transmitted to the patientnotes database 402 or the EMR database 404 and/or to a personal computeror mobile device of a clinic operator.

FIG. 6 is not intended to be limiting; the method 600 can include moreor fewer steps and/or processes than those illustrated in FIG. 6. Any orall of the steps of method 600 may be implemented during a telemedicinesession or at any other desired time.

FIG. 7 illustrates a computer-implemented method 700 for a medicalsystem processing medical claims. The method 700 may be implemented on asystem including a processor, such as the processor 106, and a memorydevice, such as the memory device 108. The method 700 may be implementedon a processor configured to perform the steps of the method 700. Themethod may be implemented on the medical system 100. The method 700 mayinclude operations that are implemented in computer instructions storedin a memory device, such as the memory device 108, and executed by aprocessor, such as the processor 106, of a computing device, such as thecomputing device 104. The steps of the method 700 may be stored in anon-transient computer-readable storage medium.

At step 702, the method 700 can include transmitting thedevice-generated information to a clinic server. The clinic server maybe the clinic server 302. The medical device may include the medicaldevice 102. The medical device may include the medical system 100. Thedevice-generated information may include medical coding or medicalresult information.

At step 704, the method 700 can include transmitting device-generatedinformation to the clinic server 302.

At step 706, the method 700 can include causing the clinic server 302,using the device-generated information, to determine device-basedmedical coding information. This determination can includecross-referencing information about actions performed by the medicaldevice 102 with a reference list associating those actions with certainmedical codes and/or identifying a portion of the device-generatedinformation containing medical coding information.

At step 708, the method 700 can include causing the clinic server 302 todetermine device-based medical result information using thedevice-generated information. This determination can include determiningthat the device-generated information includes test results (such as ablood glucose measurement).

At step 710, the method 700 can include causing the clinic server 302 totransmit the medical result information to a patient notes database. Thepatient notes database can include the patient notes database 402.

At step 712, the method 700 can include causing the clinic server 302 totransmit the device-based medical coding information to the EMRdatabase. The EMR database can include the EMR database 404.

At step 714, the method 700 can include causing the clinic server 302 toreceive from the EMR database 404 reviewed medical coding information.

At step 716, using the reviewed medical coding information and thedevice-based medical coding information, the method 700 can includecausing the clinic server 302 to determine a match indicator. The matchindicator indicates whether the reviewed medical coding information canbe reconciled with the device-based medical coding information. Examplesof such determination include (i) cross-referencing the reviewed medicalcoding information with the device-based medical coding informationand/or (ii) cross-referencing both the reviewed medical codinginformation and the device-based medical coding information with adatabase to generate the match indicator. For instance, the device-basedmedical coding information for a CT scan of a knee may be reconcilablewith reviewed medical coding information of patient being fitted for aknee brace, but not reconcilable with reviewed medical codinginformation of a patient being fitted for an elbow brace.

At step 718, the method 700 can include causing the clinic server 302 totransmit the device-based medical coding information to a claimadjudication server while bypassing the EMR database 404 and the billerserver 406. The claim adjudication server may be the claim adjudicationserver 408. By transmitting the device-based medical coding informationdirectly to the claim adjudication server 408, fewer total data packetsmay be sent, reducing network loads.

At step 720, the method 700 can include causing the clinic server 302 totransmit the determination. The determination may be transmitted to theclaim adjudication server. The claim adjudication server may be theclaim adjudication server 408. The determination may be transmitted tothe biller server. The biller server may be the biller server 406. Thedetermination may be transmitted to the patient notes database 402 orthe EMR database 404. The determination may be transmitted to a personalcomputer or mobile device of a clinic operator.

FIG. 7 is not intended to be limiting; the method 700 can include moreor fewer steps and/or processes than those illustrated in FIG. 7. Any orall of the steps of method 700 may be implemented during a telemedicinesession or at any other desired time.

FIG. 8 shows an example computer system 800 which can perform any one ormore of the methods described herein, in accordance with one or moreaspects of the present disclosure. In one example, computer system 800may include a computing device and correspond to an assistanceinterface, a reporting interface, a supervisory interface, a clinicianinterface, a server (including an AI engine), a patient interface, anambulatory sensor, a goniometer, a treatment device 10, a medical device102, a pressure sensor, or any suitable component. The computer system800 may be capable of executing instructions implementing the one ormore machine learning models of the artificial intelligence engine. Thecomputer system may be connected (e.g., networked) to other computersystems in a LAN, an intranet, an extranet, or the Internet, includingvia the cloud or a peer-to-peer network. The computer system may operatein the capacity of a server in a client-server network environment. Thecomputer system may be a personal computer (PC), a tablet computer, awearable (e.g., wristband), a set-top box (STB), a personal DigitalAssistant (PDA), a mobile phone, a camera, a video camera, an Internetof Things (IoT) device, or any device capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that device. Further, while only a single computer system isillustrated, the term “computer” shall also be taken to include anycollection of computers that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of the methodsdiscussed herein.

The computer system 800 includes a processing device 802, a main memory804 (e.g., read-only memory (ROM), flash memory, solid state drives(SSDs), dynamic random access memory (DRAM) such as synchronous DRAM(SDRAM)), a static memory 806 (e.g., flash memory, solid state drives(SSDs), static random access memory (SRAM)), and a data storage device808, which communicate with each other via a bus 810.

Processing device 802 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processing device 802 may be a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, or a processor implementing other instruction sets orprocessors implementing a combination of instruction sets. Theprocessing device 802 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), asystem on a chip, a field programmable gate array (FPGA), a digitalsignal processor (DSP), network processor, or the like. The processingdevice 802 is configured to execute instructions for performing any ofthe operations and steps discussed herein.

The computer system 800 may further include a network interface device812. The computer system 800 also may include a video display 814 (e.g.,a liquid crystal display (LCD), a light-emitting diode (LED), an organiclight-emitting diode (OLED), a quantum LED, a cathode ray tube (CRT), ashadow mask CRT, an aperture grille CRT, a monochrome CRT), one or moreinput devices 816 (e.g., a keyboard and/or a mouse or a gaming-likecontrol), and one or more speakers 818 (e.g., a speaker). In oneillustrative example, the video display 814 and the input device(s) 816may be combined into a single component or device (e.g., an LCD touchscreen).

The data storage device 816 may include a computer-readable medium 820on which the instructions 822 embodying any one or more of the methods,operations, or functions described herein is stored. The instructions822 may also reside, completely or at least partially, within the mainmemory 804 and/or within the processing device 802 during executionthereof by the computer system 800. As such, the main memory 804 and theprocessing device 802 also constitute computer-readable media. Theinstructions 822 may further be transmitted or received over a networkvia the network interface device 812.

While the computer-readable storage medium 820 is shown in theillustrative examples to be a single medium, the term “computer-readablestorage medium” should be taken to include a single medium or multiplemedia (e.g., a centralized or distributed database, and/or associatedcaches and servers) that store the one or more sets of instructions. Theterm “computer-readable storage medium” shall also be taken to includeany medium that is capable of storing, encoding or carrying a set ofinstructions for execution by the machine and that cause the machine toperform any one or more of the methodologies of the present disclosure.The term “computer-readable storage medium” shall accordingly be takento include, but not be limited to, solid-state memories, optical media,and magnetic media.

FIG. 8 is not intended to be limiting; the system 800 may include moreor fewer components than those illustrated in FIG. 8.

The term “computer-readable storage medium” should be taken to include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore sets of instructions. The term “computer-readable storage medium”shall also be taken to include any medium capable of storing, encodingor carrying a set of instructions for execution by the machine andcausing the machine to perform any one or more of the methodologies ofthe present disclosure. The term “computer-readable storage medium”shall accordingly be taken to include, but not be limited to,solid-state memories, optical media, and magnetic media.

Any of the systems and methods described in this disclosure may be usedin connection with rehabilitation. Unless expressly stated otherwise, isto be understood that rehabilitation includes prehabilitation (alsoreferred to as “pre-habilitation” or “prehab”). Prehabilitation may beused as a preventative procedure or as a pre-surgical or pre-treatmentprocedure. Prehabilitation may include any action performed by or on apatient (or directed to be performed by or on a patient, including,without limitation, remotely or distally through telemedicine) to,without limitation, prevent or reduce a likelihood of injury (e.g.,prior to the occurrence of the injury); improve recovery time subsequentto surgery; improve strength subsequent to surgery; or any of theforegoing with respect to any non-surgical clinical treatment plan to beundertaken for the purpose of ameliorating or mitigating injury,dysfunction, or other negative consequence of surgical or non-surgicaltreatment on any external or internal part of a patient's body. Forexample, a mastectomy may require prehabilitation to strengthen musclesor muscle groups affected directly or indirectly by the mastectomy. As afurther non-limiting example, the removal of an intestinal tumor, therepair of a hernia, open-heart surgery or other procedures performed oninternal organs or structures, whether to repair those organs orstructures, to excise them or parts of them, to treat them, etc., canrequire cutting through and harming numerous muscles and muscle groupsin or about, without limitation, the abdomen, the ribs and/or thethoracic cavity. Prehabilitation can improve a patient's speed ofrecovery, measure of quality of life, level of pain, etc. in all theforegoing procedures. In one embodiment of prehabilitation, apre-surgical procedure or a pre-non-surgical-treatment may include oneor more sets of exercises for a patient to perform prior to suchprocedure or treatment. The patient may prepare an area of his or herbody for the surgical procedure by performing the one or more sets ofexercises, thereby strengthening muscle groups, improving existingand/or establishing new muscle memory, enhancing mobility, improvingblood flow, and/or the like.

In some embodiments, the systems and methods described herein may useartificial intelligence and/or machine learning to generate aprehabilitation treatment plan for a user. Additionally, oralternatively, the systems and methods described herein may useartificial intelligence and/or machine learning to recommend an optimalexercise machine configuration for a user. For example, a data model maybe trained on historical data such that the data model may be providedwith input data relating to the user and may generate output dataindicative of a recommended exercise machine configuration for aspecific user. Additionally, or alternatively, the systems and methodsdescribed herein may use machine learning and/or artificial intelligenceto generate other types of recommendations relating to prehabilitation,such as recommended reading material to educate the patient, arecommended health professional specialist to contact, and/or the like.

Consistent with the above disclosure, the examples of systems and methodenumerated in the following clauses are specifically contemplated andare intended as a non-limiting set of examples.

Clause 1. A computer-implemented system for processing medical claims,comprising:

a medical device configured to be manipulated by a user while the userperforms a treatment plan;

a patient interface associated with the medical device, the patientinterface comprising an output configured to present telemedicineinformation associated with a telemedicine session; and

a processor configured to:

-   -   during the telemedicine session, receive device-generated        information from the medical device;    -   using the device-generated information, determine device-based        medical coding information; and    -   transmit the device-based medical coding information to a claim        adjudication server.

Clause 2. The computer-implemented system of any clause herein, wherein,during the telemedicine session, the device-generated information isgenerated by the medical device.

Clause 3. The computer-implemented system of any clause herein, wherein,using the device-generated information, the processor is furtherconfigured to determine device-based medical result information.

Clause 4. The computer-implemented system of any clause herein, whereinthe processor is further configured to transmit the device-based medicalresult information to a patient notes database.

Clause 5. The computer-implemented system of any clause herein, whereinthe processor is further configured to transmit the device-based medicalcoding information to an electronic medical records database.

Clause 6. The computer-implemented system of any clause herein, whereinthe processor is further configured to:

receive reviewed medical coding information from an electronic medicalrecords database, wherein, using the reviewed medical coding informationand the device-based medical coding information, the processor isfurther configured to determine a match indicator; and

transmit the match indicator to the claim adjudication server.

Clause 7. A system for processing medical claims, comprising:

a processor configured to:

-   -   receive device-generated information from a medical device;    -   using the device-generated information, determine device-based        medical coding information; and    -   transmit the device-based medical coding information to a claim        adjudication server.

Clause 8. The system of any clause herein, wherein the device-generatedinformation is generated by the medical device.

Clause 9. The system of any clause herein, wherein, using thedevice-generated information, the processor is further configured todetermine device-based medical result information.

Clause 10. The system of any clause herein, wherein the processor isfurther configured to transmit the device-based medical resultinformation to a patient notes database.

Clause 11. The system of any clause herein, wherein the processor isfurther configured to transmit the device-based medical codinginformation to an electronic medical records database.

Clause 12. The system of any clause herein, wherein the processor isfurther configured to receive reviewed medical coding information froman electronic medical records database.

Clause 13. The system of any clause herein, wherein, using the reviewedmedical coding information and the device-based medical codinginformation, the processor is further configured to determine a matchindicator.

Clause 14. The system of any clause herein, wherein the processor isfurther configured to transmit the match indicator to the claimadjudication server.

Clause 15. The system of any clause herein, further comprising a memorydevice operatively coupled to the processor, wherein the memory devicestores instructions, and wherein the processor is configured to executethe instructions.

Clause 16. A method for a clinic server processing medical claims,comprising:

receiving device-generated information from a medical device; using thedevice-generated information, determining device-based medical codinginformation; and transmitting the device-based medical codinginformation to a claim adjudication server.

Clause 17. The method of any clause herein, wherein the device-generatedinformation is generated by the medical device.

Clause 18. The method of any clause herein, further comprising using thedevice-generated information to determine device-based medical resultinformation.

Clause 19. The method of any clause herein, further comprisingtransmitting the device-based medical result information to a patientnotes database.

Clause 20. The method of any clause herein, further comprisingtransmitting the device-based medical coding information to anelectronic medical records database.

Clause 21. The method of any clause herein, further comprising receivingreviewed medical coding information from an electronic medical recordsdatabase.

Clause 22. The method of any clause herein, further comprisingdetermining, using the reviewed medical coding information and thedevice-based medical coding information, a match indicator.

Clause 23. The method of any clause herein, further comprisingtransmitting the match indicator to the claim adjudication server.

Clause 24. A tangible, non-transitory computer-readable medium storinginstructions that, when executed, cause a processor to:

receive device-generated information from a medical device;

using the device-generated information, determine device-based medicalcoding information; and

transmit the device-based medical coding information to a claimadjudication server.

Clause 25. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the device-generated information is generated bythe medical device.

Clause 26. The tangible, non-transitory computer-readable medium of anyclause herein, wherein, using the device-generated information, theinstructions further cause the processor to determine device-basedmedical result information.

Clause 27. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor totransmit the device-based medical result information to a patient notesdatabase.

Clause 28. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor totransmit the device-based medical coding information to an electronicmedical records database.

Clause 29. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the processor is further configured to receivereviewed medical coding information from an electronic medical recordsdatabase.

Clause 30. The tangible, non-transitory computer-readable medium of anyclause herein, wherein, using the reviewed medical coding informationand the device-based medical coding information, the instructionsfurther cause the processor to determine a match indicator.

Clause 31. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor totransmit the match indicator to the claim adjudication server.

Clause 32. A system for generating and processing medical billing codes,comprising:

a medical device; and

a computing device comprising a processor in communication with themedical device, wherein the processor is configured to:

-   -   receive device-generated information from the medical device;    -   transmit the device-generated information to a clinic server;    -   using the device-generated information, cause the clinic server        to determine device-based medical coding information; and    -   cause the clinic server to transmit the device-based medical        coding information to a claim adjudication server.

Clause 33. The system of any clause herein, wherein the device-generatedinformation is generated by the medical device.

Clause 34. The system of any clause herein, wherein, using thedevice-generated information, the processor is further configured tocause the clinic server to determine device-based medical resultinformation.

Clause 35. The system of any clause herein, wherein the processor isfurther configured to cause the clinic server to transmit thedevice-based medical result information to a patient notes database.

Clause 36. The system of any clause herein, wherein the processor isfurther configured to cause the clinic server to transmit thedevice-based medical coding information to an electronic medical recordsdatabase.

Clause 37. The system of any clause herein, wherein the processor isfurther configured to cause the clinic server to receive reviewedmedical coding information from an electronic medical records database.

Clause 38. The system of any clause herein, wherein the processor isfurther configured to cause the clinic server to, using the reviewedmedical coding information and the device-based medical codinginformation, determine a match indicator.

Clause 39. The system of any clause herein, wherein the processor isfurther configured to cause the clinic server to transmit the matchindicator to the claim adjudication server.

Clause 40. The system of any clause herein, wherein the computing deviceis operatively coupled to the medical device.

Clause 41. The system of any clause herein, wherein the computing deviceis integral to the medical device.

Clause 42. The system of any clause herein, further comprising a memorydevice operatively coupled to the processor, wherein the memory devicestores instructions, and wherein the processor is configured to executethe instructions.

Clause 43. A method for operating a medical device, the methodcomprising:

receiving device-generated information from the medical device

transmitting the device-generated information to a clinic server;

using the device-generated information, causing the clinic server todetermine device-based medical coding information; and

causing the clinic server to transmit the device-based medical codinginformation to a claim adjudication server.

Clause 44. The method of any clause herein, wherein the device-generatedinformation is generated by the medical device.

Clause 45. The method of any clause herein, further comprising using thedevice-generated information to cause the clinic server to determinedevice-based medical result information.

Clause 46. The method of any clause herein, further comprising causingthe clinic server to transmit the device-based medical resultinformation to a patient notes database.

Clause 47. The method of any clause herein, further comprising causingthe clinic server to transmit the device-based medical codinginformation to an electronic medical records database.

Clause 48. The method of any clause herein, further comprising causingthe clinic server to receive reviewed medical coding information from anelectronic medical records database.

Clause 49. The method of any clause herein, further comprising causingthe clinic server to determine a match indicator.

Clause 50. The method of any clause herein, further comprising causingthe clinic server to transmit the match indicator to the claimadjudication server by using the reviewed medical coding information andthe device-based medical coding information.

Clause 51. A tangible, non-transitory computer-readable medium storinginstructions that, when executed, cause a processor to:

receive device-generated information from a medical device;

transmit the device-generated information to a clinic server;

using the device-generated information, cause the clinic server todetermine device-based medical coding information; and

cause the clinic server to transmit the device-based medical codinginformation to a claim adjudication server.

Clause 52. The tangible, non-transitory computer-readable medium if anyclause herein, wherein the device-generated information is generated bythe medical device.

Clause 53. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor tocause the clinic server to determine device-based medical resultinformation.

Clause 54. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor tocause the clinic server to transmit the device-based medical resultinformation to a patient notes database.

Clause 55. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor tocause the clinic server to transmit the device-based medical codinginformation to an electronic medical records database.

Clause 56. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor tocause the clinic server to receive reviewed medical coding informationfrom an electronic medical records database.

Clause 57. The tangible, non-transitory computer-readable medium of anyclause herein, wherein, using the reviewed medical coding informationand the device-based medical coding information, the instructionsfurther cause the processor to cause the clinic server to determine amatch indicator.

Clause 58. The tangible, non-transitory computer-readable medium of anyclause herein, wherein the instructions further cause the processor tocause the clinic server to transmit the match indicator to the claimadjudication server.

No part of the description in this application should be read asimplying that any particular element, step, or function is an essentialelement that must be included in the claim scope. The scope of patentedsubject matter is defined only by the claims. Moreover, none of theclaims is intended to invoke 35 U.S.C. § 112(f) unless the exact words“means for” are followed by a participle.

The foregoing description, for purposes of explanation, use specificnomenclature to provide a thorough understanding of the describedembodiments. However, it should be apparent to one skilled in the artthat the specific details are not required in order to practice thedescribed embodiments. Thus, the foregoing descriptions of specificembodiments are presented for purposes of illustration and description.They are not intended to be exhaustive or to limit the describedembodiments to the precise forms disclosed. It should be apparent to oneof ordinary skill in the art that many modifications and variations arepossible in view of the above teachings.

The above discussion is meant to be illustrative of the principles andvarious embodiments of the present invention. Once the above disclosureis fully appreciated, numerous variations and modifications will becomeapparent to those skilled in the art. It is intended that the followingclaims be interpreted to embrace all such variations and modifications.

What is claimed is:
 1. A computer-implemented system for processingmedical claims, comprising: a medical device configured to bemanipulated by a user while the user performs a treatment plan; apatient interface associated with the medical device, the patientinterface comprising an output configured to present telemedicineinformation associated with a telemedicine session; and a processorconfigured to: during the telemedicine session, receive device-generatedinformation from the medical device; using the device-generatedinformation, determine device-based medical coding information; andtransmit the device-based medical coding information to a claimadjudication server.
 2. The computer-implemented system of claim 1,wherein, during the telemedicine session, the device-generatedinformation is generated by the medical device.
 3. Thecomputer-implemented system of claim 1, wherein, using thedevice-generated information, the processor is further configured todetermine device-based medical result information.
 4. Thecomputer-implemented system of claim 3, wherein the processor is furtherconfigured to transmit the device-based medical result information to apatient notes database.
 5. The computer-implemented system of claim 1,wherein the processor is further configured to transmit the device-basedmedical coding information to an electronic medical records database. 6.The computer-implemented system of claim 1, wherein the processor isfurther configured to: receive reviewed medical coding information froman electronic medical records database, wherein, using the reviewedmedical coding information and the device-based medical codinginformation, the processor is further configured to determine a matchindicator; and transmit the match indicator to the claim adjudicationserver.
 7. A system for processing medical claims, comprising: aprocessor configured to: receive device-generated information from amedical device; using the device-generated information, determinedevice-based medical coding information; and transmit the device-basedmedical coding information to a claim adjudication server.
 8. The systemof claim 7, wherein the device-generated information is generated by themedical device.
 9. The system of claim 7, wherein, using thedevice-generated information, the processor is further configured todetermine device-based medical result information.
 10. The system ofclaim 9, wherein the processor is further configured to transmit thedevice-based medical result information to a patient notes database. 11.The system of claim 7, wherein the processor is further configured totransmit the device-based medical coding information to an electronicmedical records database.
 12. The system of claim 7, wherein theprocessor is further configured to receive reviewed medical codinginformation from an electronic medical records database.
 13. The systemof claim 12, wherein, using the reviewed medical coding information andthe device-based medical coding information, the processor is furtherconfigured to determine a match indicator.
 14. The system of claim 13,wherein the processor is further configured to transmit the matchindicator to the claim adjudication server.
 15. The system of claim 7,further comprising a memory device operatively coupled to the processor,wherein the memory device stores instructions, and wherein the processoris configured to execute the instructions.
 16. A method for a clinicserver processing medical claims, comprising: receiving device-generatedinformation from a medical device; using the device-generatedinformation, determining device-based medical coding information; andtransmitting the device-based medical coding information to a claimadjudication server.
 17. The method of claim 16, wherein thedevice-generated information is generated by the medical device.
 18. Themethod of claim 16, further comprising using the device-generatedinformation to determine device-based medical result information. 19.The method of claim 18, further comprising transmitting the device-basedmedical result information to a patient notes database.
 20. The methodof claim 16, further comprising transmitting the device-based medicalcoding information to an electronic medical records database.
 21. Themethod of claim 16, further comprising receiving reviewed medical codinginformation from an electronic medical records database.
 22. The methodof claim 21, further comprising using the reviewed medical codinginformation and the device-based medical coding information to determinea match indicator.
 23. The method of claim 22, further comprisingtransmitting the match indicator to the claim adjudication server.
 24. Atangible, non-transitory computer-readable medium storing instructionsthat, when executed, cause a processor to: receive device-generatedinformation from a medical device; using the device-generatedinformation, determine device-based medical coding information; andtransmit the device-based medical coding information to a claimadjudication server.
 25. The tangible, non-transitory computer-readablemedium of claim 24, wherein the device-generated information isgenerated by the medical device.
 26. The tangible, non-transitorycomputer-readable medium of claim 24, wherein, using thedevice-generated information, the instructions further cause theprocessor to determine device-based medical result information.
 27. Thetangible, non-transitory computer-readable medium of claim 26, whereinthe instructions further cause the processor to transmit thedevice-based medical result information to a patient notes database. 28.The tangible, non-transitory computer-readable medium of claim 24,wherein the instructions further cause the processor to transmit thedevice-based medical coding information to an electronic medical recordsdatabase.
 29. The tangible, non-transitory computer-readable medium ofclaim 24, wherein the processor is further configured to receivereviewed medical coding information from an electronic medical recordsdatabase.
 30. The tangible, non-transitory computer-readable medium ofclaim 29, wherein, using the reviewed medical coding information and thedevice-based medical coding information, the instructions further causethe processor to determine a match indicator.